RFP-003: unblock atomic swaps, add LEZ primitive status#48
Open
fryorcraken wants to merge 2 commits intomasterfrom
Open
RFP-003: unblock atomic swaps, add LEZ primitive status#48fryorcraken wants to merge 2 commits intomasterfrom
fryorcraken wants to merge 2 commits intomasterfrom
Conversation
The "blocked pending LEZ timelock support" banner is no longer accurate — BlockValidityWindow and TimestampValidityWindow exist on logos-execution-zone main. Replace it with a "ready to start" status and add an LEZ Primitive Status section so applicants can reason about the LEZ side without first auditing the source: file-cited inventory of present primitives (BIP-340 Schnorr, WitnessSet 2-of-2, validity windows, clock program, SHA-256), the two design constraints (Schnorr verify lives at the witness/auth layer not as an in-guest syscall; no native n-of-m threshold), and two open questions applicants should confirm early (s-malleability after acceptance; validity-window enforcement timing). Tighten Bitcoin references with DLC-specs AdaptorSignature.md, Aumayr et al. 2021, and secp256kfun; fix the Fournier link. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The "no native n-of-m threshold" constraint was overstated. WitnessSet validates every (sig, pubkey) pair independently, so a guest program can apply its own threshold policy over the validated signer set with no syscall needed. The actual constraint is narrower: a program cannot verify an *arbitrary* (message, sig, pubkey) triple — e.g. a stored signature from prior off-chain coordination. The swaps in this RFP do not hit that case. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BlockValidityWindowandTimestampValidityWindowexist onlogos-execution-zonemaintoday. Replaces it with a "ready to start" status.WitnessSet2-of-2, validity windows,clockprogram, SHA-256), two design constraints (Schnorr verify at the witness/auth layer not as an in-guest syscall; no native n-of-m threshold), and two open questions applicants should confirm early (s-malleability after acceptance; validity-window enforcement timing).AdaptorSignature.md(canonical spec with test vectors), Aumayr et al. 2021 (formal security defs), andsecp256kfun/ecdsa-fun. Fixes the Fournier link (one-time-vrf→one-time-VES).The functional/usability/reliability requirements are unchanged.
Test plan
RFPs/RFP-003-atomic-swaps.mdand confirm the new section anchors and table render correctlylogos-execution-zonemainone-time-VES,secp256kfun) resolve🤖 Generated with Claude Code